Skip to content

Trigger podman.io version bump from release action #26181

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
May 27, 2025
Merged

Trigger podman.io version bump from release action #26181

merged 1 commit into from
May 27, 2025

Conversation

ashley-cui
Copy link
Member

Our release is created by a GitHub action, and GitHub prevents workflows from running on events that were caused by other workflows to prevent unlimited recursion. To get around this, use a reusable workflow to trigger the podman.io version bump from the release action.

Does this PR introduce a user-facing change?

None

@ashley-cui
Trigger podman.io version bump from release action
416bb84 
Our release is created by a GitHub action, and GitHub prevents workflows from running on events that were caused by other workflows to prevent unlimited recursion.
To get around this, use a reusable workflow to trigger the podman.io version bump from the release action.

Signed-off-by: Ashley Cui <[email protected]>
@openshift-ci openshift-ci bot added release-note-none approved Indicates a PR has been approved by an approver from all required OWNERS files. labels May 22, 2025
Luap99
Luap99 approved these changes May 22, 2025
View reviewed changes
Copy link
Member

@Luap99 Luap99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented May 22, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ashley-cui, Luap99

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@baude
Copy link
Member

baude commented May 27, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 27, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit fec6e69 into containers:main May 27, 2025
33 of 37 checks passed
@Luap99
Copy link
Member

Luap99 commented May 27, 2025

@ashley-cui Does this need to be backport to the 5.5 branch or does the action trigger of main?

@ashley-cui
Copy link
Member Author

@Luap99 I think its off main, but a backport won't hurt anyway.

/cherry-pick v5.5

@openshift-cherrypick-robot
Copy link
Collaborator

@ashley-cui: #26181 failed to apply on top of branch "v5.5":

Applying: Trigger podman.io version bump from release action
Using index info to reconstruct a base tree...
M	RELEASE_PROCESS.md
Falling back to patching base and 3-way merge...
Auto-merging RELEASE_PROCESS.md
CONFLICT (content): Merge conflict in RELEASE_PROCESS.md
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Trigger podman.io version bump from release action

In response to this:

@Luap99 I think its off main, but a backport won't hurt anyway.

/cherry-pick v5.5

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Luap99 Luap99 Luap99 approved these changes

Assignees

@baude baude

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. release-note-none
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@ashley-cui @baude @Luap99 @openshift-cherrypick-robot